Method, system, and program for returning data to read requests received over a bus

ABSTRACT

Provided are a method, system, and program for receiving a read request that is one of a plurality of read requests directed toward sequential data and determining whether at least one previous read request for sequential data preceding the data requested by the received read request was not processed. Data is returned to the received read request in response to returning data to the at least one previous read request.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a system, method, and program for returning data to read requests received over a bus.

2. Description of the Related Art

FIG. 1 illustrates a prior art storage device architecture, where an external bus master 2, such as a network adaptor (e.g., a Fibre Channel controller, Ethernet controller, etc.) may access data in one or more disks 4, 6 through a Serial Advanced Technology Attachment (SATA) controller 8 over a Peripheral Component Interconnect (PCI) bus 10, which may utilize the Peripheral Component Interconnect (PCI) or PCI-X protocol. In prior art systems, data being transferred between the external bus master 2 and SATA controller 8 first typically flows through a memory controller 12 and memory 14, such as a Static Dynamic Random Access Memory (SDRAM). For instance, when the external bus master 2 wants to write data to the disks 4, 6, the external bus master 2 may transfer the data to the memory 14. The SATA controller 8 may then read the data sent to the memory 14 in the write request and write the data to disk 4, 6. For a read operation, the SATA controller 8 typically transfers requested read data to the memory 14 and the external bus master 2 typically accesses the read data from the memory 14. The controllers 2 and 8 may include Direct Memory Access (DMA) engines that perform the actual data movement operations therebetween through the memory 14.

Further, in the PCI-X prior art, the memory buffer 14 enables read and write bursts between an external bus master 2 and a SATA controller 8, because current SATA controllers must operate as a bus master to handle burst data transfers. Further details of the PCI and PCI-X protocol are described in the publications “PCI Local Bus Specification”, Rev. 2.3 (PCI Special Interest Group, March 2002) and “PCI-X Addendum to the PCI Local Bus Specification”, Rev. 1.0a (PCI Special Interest Group, July 2000).

Using the memory 14 component to buffer data being transferred between the controllers 2 and 8 provides additional latency and delays because of the additional read and write operations involved in using the memory 14 as an intermediary buffer. For these reasons, there is a need in the art for improved techniques for transferring data between controllers in a bus architecture.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers represent corresponding parts throughout:

FIG. 1 illustrates a bus architecture for accessing data in storage devices as known in the prior art;

FIG. 2 illustrates a bus architecture for accessing data in storage devices in accordance with embodiments of the invention;

FIG. 3 illustrates configuration registers of a disk controller in accordance with embodiments of the invention;

FIGS. 4 and 5 illustrate logic for handling I/O requests in accordance with embodiments of the invention;

FIG. 6 illustrates registers that are configured in accordance with embodiments of the invention;

FIG. 7 illustrates logic to configure a device controller in accordance with embodiments of the invention;

FIG. 8 illustrates logic to configure an external bus master in accordance with embodiments of the invention;

FIG. 9 illustrates a Direct Memory Access (DMA) descriptor table utilized with embodiments of the invention;

FIG. 10 illustrates logic to process a DMA descriptor table in accordance with embodiments of the invention;

FIG. 11 illustrates an alternative bus architecture for accessing data in storage devices in accordance with embodiments of the invention;

FIG. 12 illustrates fields in a request that are queued during read request processing in accordance with embodiments of the invention;

FIG. 13 illustrates logic to return data to read requests in accordance with embodiments of the invention; and

FIG. 14 illustrates an example of how read requests are processed in accordance with embodiments of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.

Transferring Data Requests Directly Between an External Bus Master and a Disk Controller

FIG. 2 illustrates a computing environment in which aspects of the invention are implemented. A storage system 50, such as a disk array, (e.g., Just a Bunch of Disks (JBOD), Redundant Array of Independent Disks (RAID) array, etc.) includes an external bus master 52, which is an external bus master capable of initiating memory requests to a disk controller 54 that manages access to the disks 60 a . . . 60 n. External bus master 52 may include a Direct Memory Access (DMA) engine 56. Disk controller 54 includes a Direct Memory Access (DMA) engine 58 to handle I/O operations for the controller 54. The disk controller 54 may implement a disk access protocol, such as SATA, ATA, Small Computer System Interface (SCSI), Integrated Drive Electronics (IDE), etc. The disk controller 54 enables access to one or more disk drives 60 a . . . 60 n. The disk controller 54 includes a buffer 64 in which data read from the disks 60 a . . . 60 n and write data being transferred to the disks 60 a . . . 60 n is buffered before being transferred to the initiator. The disk controller 54 may include a component, such as a serial engine in embodiments where the disk controller 54 comprises a SATA controller, to write data in the buffer 64 to the disks 60 a . . . 60 n. The external bus master 52 may comprise a network adaptor that receives I/O requests from devices over a network directed to the disks 60 a . . . . 60 n.

An I/O processor 70, such as the Intel Corporation (Intel®) IQ80310 processor, manages system operations and programs the I/O controller DMA engine 56 to read and write data at a specified address and perform other I/O management related operations. In certain embodiments, the I/O processor 70 connects to a PCI bus 72 that enables communication among the external bus master 52, disk controller 54, and I/O processor 70 to execute an I/O command received from the host processor. The external bus master 52, disk controller 54, and I/O processor 70 may be implemented on one or more PCI add-on cards that communicate over the bus 72. For instance, the I/O processor 70 and disk controller 54 may be implemented on a same PCI card and the external bus master 52 may be implemented on a different PCI card, such as a network adaptor card. The bus 72 may conform to the PCI or PCI-X protocols or any other communication protocol known in the art. Further details of the PCI-X protocol are described in the publication “PCI-X Specification Rev. 1.0a”, published by PCISIG.

In embodiments where the external bus master 52 comprises a network adaptor card, such as a Fibre Channel adaptor, the I/O processor 70 may receive the I/O command through the adaptor, and then configure the external bus master 52 and disk controller 54 to transfer data as described below.

In certain embodiments, the disk controller 54 is configured to have an address window which comprises a range of addresses that may be randomly accessed and used to transfer data directly between the external bus master 52 and the disk controller buffer 64. The address window is a range of addresses that when requested cause the disk controller 54 to claim access to the request on the bus 72 and respond to the external bus master 52 request directly. The external bus master DMA 56 may utilize addresses from the address window randomly or in sequential order. The external bus master DMA 56 may thus push and pull data from the disk by accessing a memory space in the address window. Further, for any request, the DMA 56 may use any address in the window to transmit the request to the disk controller 54. The DMA engine 56 in the external bus master 52 may be configured by the I/O processor 70 to interface directly with the disk controller 54 using addresses in the address window.

FIG. 3 illustrates disk controller 52 configuration registers 80 to which the the I/O processor 70 writes to configure the bus 72 for I/O operations. The settings that may be written by the I/O processor in the configuration registers 80 comprise:

address window 82: a range of addresses that an initiator, such as the external bus master 52 may use to communicate directly with the disk controller 54 and buffer 64 therein.

DMA Mode 84: indicates whether the DMA engine is used for the I/O operations.

Read/Write Operation (OP) 86: indicates whether the received requests are to be processed as read or write operations to the disks 60 a . . . 60 n.

Burst Slave Mode 88: Indicates whether the initiator will operate in burst slave mode, enabling the disk controller to respond to burst memory requests from the external bus master 52.

FIG. 4 illustrates interactive operations implemented among the external bus master 52, disk controller 54, and I/O processor 70 to write data to the disks 60 a . . . 60 n in accordance with embodiments of the invention. Blocks 100 and 102 may be executed by the I/O processor 70. At block 100, the I/O processor 70 programs the external bus master 52 to fetch data from an external source. For instance, in embodiments where the I/O processor 70 comprises a host bus adaptor, the external source may comprise an external host submitting I/O write requests directed to the disks 60 a . . . 60 n. The I/O processor 70 further programs (at block 102) the external bus master DMA engine 56 to transfer the fetched data in burst sized packets to addresses in the address window of the disk controller 54 on the bus 72. The I/O processor 70 programs (at block 104) the disk controller 54 configuration registers 80 to disable DMA mode 84 in the disk controller 54, and enable burst mode by setting field 88.

In response to being configured (at blocks 100 and 102), the external bus master 52 may receive (at block 120) data fetched from the external source. Blocks 120-124 illustrate operations, or logic, implemented by the external bus master 52 when configured by the I/O processor 70. The external bus master 52 then divides (at block 122) the data to write into burst size blocks to transfer to addresses in the disk controller 54 address window over the bus 72. The DMA engine 56 then transfers (at block 124) write requests including the smaller blocks of fetched data to an address in the address window. In certain embodiments, such as PCI-X embodiments, the DMA engine 56 transfers data in burst mode (utilizing memory requests) to allow for the transfer of greater amounts of data.

Blocks 140-144 illustrate operations performed by the disk controller 54 to handle write operations to the address window to the disks 60 a . . . 60 n. At block 140, the disk controller 54 claims access over the write requests transmitted over the bus 72 to an address in the address window. Because the DMA mode 84 is disabled and write is indicated in the operation field 86, the disk controller 54 (at block 142) adds the received data to the buffer 64 according to the buffering scheme, which may be First-In-First-Out (FIFO). The disk controller 54 then transfers (at block 144) buffered data to the target disk 60 a . . . 60 n. As discussed, the disk controller 54 may include a serial engine to transfer write data in the buffer 64 to the disks 60 a . . . 60 n.

FIG. 5 illustrates operations performed by the external bus master 52, disk controller 54, and I/O processor 70 to transfer data from the disks 60 a . . . 60 n to the external bus master 52 in accordance with embodiments of the invention. Blocks 200 and 202 illustrate operations performed by the I/O processor 70 to configure the storage system 50 for a read operation, which may be initiated by an external host system and transmitted over a network to the external bus master 52, comprising a host bus adaptor. At block 200, the I/O processor 70 configures the disk controller 54 configuration registers 80 to disable DMA mode in field 84, and enable burst mode in field 88. The I/O processor 70 further configures (at block 202) the external bus master 52 DMA engine 56 to request a specified amount of data in the disk controller 54 address window. In PCI-X embodiments, the I/O processor 70 may configure the external bus master 52 to issue burst read requests, where each request comprises an address in the address window and a byte count of data to read, e.g., 512 bytes. The address window comprises a non-prefetchable region, since data is destroyed (replaced with new data from disks 60 a, 60 b . . . 60 n) once it has been read from buffer 64 of the disk controller 54.

Blocks 210, 212, and 214 illustrate operations performed by the external bus master DMA engine 56 to submit the read requests. At blocks 210 and 212, the DMA engine 56 constructs read requests having burst block sizes as set by the I/O processor 70 to addresses in the address window of the disk controller 54. The DMA engine 56 then transfers (at block 214) the read requests to the address window along with the byte count of the transfer length.

Blocks 220, 222, 224, 226, and 228 illustrate operations performed by the disk controller 54 to process the burst read request. At block 220, the disk controller 54 retrieves the data from the target disk 60 a . . . 60 n and adds (at block 222) the data to the end of the buffer 64, following the most recently added data in FIFO embodiments. Independently of buffering the data from the disk 60 a . . . 60 n, the disk controller 54 may detect (at block 224) a request to an address in the address window 82 on the bus 72 and claim (at block 226) the request. In response to the read request, the disk controller 54 may transfer (at block 228) data at the top of the buffer 64, i.e., the oldest data in the buffer, to the bus to return to the initiator of the transaction, i.e., the external bus master 52. In certain embodiments, the first in data is transferred from the buffer 64 regardless of the actual address in the address window used. Further, in non-prefetchable embodiments, once data is accessed from the buffer 64, then the data is overwritten when the next data from the disks 60 a . . . 60 n is accessed.

The described embodiments thus provide a technique to allow an initiator, such as the external bus master 52, to communicate burst data requests to a predefined address window in the disk controller 54 to cause the disk controller 54 to act as a slave and transfer write data to a target disk 60 a . . . 60 n or return read data from the buffer 64. With the described embodiments, an external bus master may communicate directly with a disk controller, such as an ATA or SATA controller, without the need for an intermediate memory device, such as shown in FIG. 1. Further, the described embodiments, allow an external bus master to burst data directly to and from a disk controller, such as an ATA controller, where the disk controller operates in burst slave mode. In this way, the described embodiments substantially reduce the latency and processor cycles needed to process I/O commands. Additionally, data that is sequentially accessed (e.g. data streaming from a disk drive) can be mapped to randomly accessed space (memory space).

Configuring the Address Window for Data Transfer Operations

In embodiments where the system 50 implements the PCI-X protocol, read requests may be transferred as a split read request. In a split read request, the external bus master 52 embodiment, acting as a bus master, transmit a read request to a memory address in the address window of the disk controller 54, which acts as a bus slave in receiving the request. When the requested data is available, the disk controller 54 embodiment then operate as a bus master and return the requested data to the external bus master 52 over the bus 72. The split read request conserves bus bandwidth because the external bus master 52 initially requesting the data does not have to continually request the read data from the disk controller 54 until the data is available, as is the case with a delayed read transaction in the PCI protocol.

The size of an I/O request to the disk controller 54 is limited to the size of the memory space allocated to the disk controller 54. For instance, if the memory space or address window for the disk controller 54 is one megabyte (Mbyte), then at most the maximum byte size of an I/O request to the disk controller 54 embodiment be one megabyte. In described embodiments, the address window may be configured independently of the size of any I/O request executed by the disk controller 54.

FIG. 6 illustrates a configuration register 250 included in the external bus master 52 that includes a maximum memory read byte count field 252 indicating the maximum byte size of any split read request that is outstanding and a maximum outstanding split transactions field 254 indicating the maximum number of outstanding split read requests at the external bus master 52. Thus, the maximum amount of address space that the external bus master 52 can address when all requests are outstanding (not yet completed), referred to herein as the “maximum assignable address space”, comprises the multiplication of the values in fields 252 and 254.

In certain embodiments, the maximum number of outstanding split read requests that can be directed to the address window of the disk controller 54 is the size of the address window divided by the maximum split read request size. Limiting the outstanding requested byte count to the size of the address window ensures that multiple outstanding split read requests will not be directed to the same memory address in the address window. If multiple outstanding split read requests are directed to the same memory address, then the external bus master 52 embodiment not be able to match returned data to the particular request.

The address window defined for the memory of the disk controller 54, in current embodiments, can extend up to a couple of gigabytes. However, the system 50 designer may want to set the address window to some smaller amount depending on the characteristics of the disk controller 54 and system 50 in which the disk controller 54 will operate. In certain embodiments, the maximum outstanding split transactions field 254 is configured based on the size of the address window, such that the maximum outstanding split transactions field 254 is set to the size of the address window (which may be configured independently of any considerations of the split read capabilities of the external bus master 52) divided by the maximum memory read byte count field 252. In this way, the maximum outstanding split read requests from the external bus master 52 will not use, at any given time, any more addresses than provided in the disk controller 54. This ensures that no one memory address in the address window will be used in concurrent multiple outstanding split read requests. In other words, the external bus master 52 will not re-use a previously used address until the previous request to the re-used address is complete. Otherwise, if the disk controller 52 received multiple split read requests using the same memory address in the address window, then the disk controller 54 embodiment not be able to determine the order in which the external bus master 52 initiated the split read requests.

FIG. 7 illustrates logic implemented in the I/O processor 70 to configure the external bus master 52 PCI registers during initialization, such as system startup or reboot. Upon beginning the configuration routine (at block 300), the I/O processor 70 configures (at block 302) the address window for the disk controller 54 to a predetermined optimal size for operations directed to the controller 54. The address window may be configured in the PCI-X configuration registers of the disk controller 54. The maximum memory read byte count 252 register in the external bus master 52 is set (at block 304) to a predetermined value, which is the maximum size of a submitted split read request. The maximum outstanding split transactions 254 is set (at block 306) to the integer result of the address window byte size divided by the maximum memory read byte count 252. If the result of the division is not an integer, then the maximum outstanding split transactions 264 embodiment comprise the integer portion of the division result. The I/O processor 70 can then perform additional (at block 308) configuration operations. After configuring the address window and external bus master registers 250 (FIG. 6), the address window to the disk controller 54 is setup to allow data to be directly transferred between an external bus master 52 without going through an external memory device on the bus 72.

FIG. 8 illustrates logic implemented in the I/O processor 70 to configure the external bus master 52 and the disk controller 54 to handle a read request submitted to the external bus master 52. Upon receiving (at block 350) an I/O request having a transfer size, the I/O processor 70 sets (at block 352) a base address to the first address in the address window and sets (at block 354) the remaining address window to the address window byte size. A remaining transfer size variable is set (at block 356) to the transfer size of the received I/O request. The I/O processor 70 then adds (at block 358) a descriptor entry in a descriptor table that defines the operations the external bus master DMA 56 performs. FIG. 9 illustrates a DMA descriptor table 400 as having a plurality of entries 402 a . . . 402 n, where each entry includes an entry number 404 a . . . 404 n, an address 406 a . . . 406 n of the memory address to which the request is directed, and a byte count 408 a . . . 408 n indicating the number of bytes involved in the request to the memory address 406 a . . . 406 n. Entries are added to a list to be processed on a First-In-First-Out (FIFO) basis. If (at block 360) the remaining address window size is zero, indicating that all addresses in the window were used in the previous descriptor entries, then the remaining address window is set (at block 362) to the address window byte size. The address 406 n for the added entry 402 n is set (at block 364) to the base address. If (at block 360) the remaining address window is not zero, then the I/O processor 70 sets (at block 366) the address 406 n in the added entry 402 n to the address plus the byte count in the immediately preceding entry 402 _(n−1).

From block 364 or 366, the I/O processor 70 sets (at block 368) the byte count 408 n for the added entry 402 n to a number of bytes that is not more than either the remaining address window or the remaining transfer size. The byte count 408 n for the added entry 402 n is then subtracted (at block 370) from both the remaining address window and remaining transfer size. If (at block 372) the remaining transfer size is zero, i.e., there are no further bytes in the received I/O request that need to be read, then the I/O processor 70 sends (at block 374) a command to the disk controller 54 to access from disk 60 a . . . . 60 n and store in buffer 564 the data requested in the I/O transaction. The I/O processor 70 also signals (at block 376) the external bus master DMA 56 to issue read requests for the entries added to the DMA descriptor table 400 to access the data that will be gathered by the disk controller 54 and stored in the buffer 64 (FIG. 2). If (at block 372) the remaining transfer size is greater than zero, i.e., there are further bytes in the received I/O request that must be processed, then control proceeds to block 358 to add another entry to the descriptor table.

With the logic of FIG. 8, the entries indicated in the descriptor table 400 can be of different byte count sizes. In certain embodiments, the I/O processor 70 can configure the external bus master 52 read request size to a value (such as 512 bytes) that is independent of the byte count size 408 a, 408 i . . . 408 n in the descriptor table entries 402 a, 402 i . . . 402 n. In certain of the embodiments, the byte count 408 a, 408 i . . . 408 n of the entry may not exceed the size of the address window. In such embodiments, the address window of the disk controller 54 must be set to a size that is capable of accommodating the maximum number of outstanding read requests 254 (FIG. 6), each having at most a byte count size equal to the maximum read byte count 252 configured for split read requests. For instance, if the maximum outstanding requests 254 is four and the maximum read byte count 252 is one kilobyte (kb), then the address window must be at least four kilobytes in size. Each descriptor entry 402 a, 402 i . . . 402 n, however, can have a byte count of four kilobytes, the address window size. In such cases, the external bus master 52, when processing a descriptor entry 402 a . . . 402 n defining a request having a byte count 408 a . . . 408 n that is greater than the maximum read byte count 252, will divide the descriptor request, which in the example is four kilobytes, into requests that do not exceed the maximum read byte count 252, e.g., one kilobyte. In this way, the byte count 408 a . . . 408 n (FIG. 9) indicated in the descriptor entries 402 a . . . 402 n are independent of the maximum read byte count 252, and is instead limited by the size of the address window. Thus, in such embodiments, the byte count 408 a . . . 408 n of a descriptor entry 402 a . . . 402 n cannot exceed the limit of the address window.

FIG. 10 illustrates logic implemented in the DMA engine 56 to process the DMA descriptor table 400 generated by the I/O processor 70 according to the logic of FIG. 8. In response (at block 450) to the signal from the I/O processor 70 to commence operations, the DMA 56 sets (at block 452) the number of outstanding split requests variable to zero. The DMA 56 then performs a loop from blocks 454 to 470 for each entry i in the DMA descriptor table 400, where i equals one to n. If (at block 456) the byte count 408 i for entry i exceeds the maximum read byte count 252 (FIG. 6), then the DMA engine 56 divides (at block 458) the request in entry i into multiple split read subrequests each not exceeding the maximum read byte count 252 to read sequential addresses from the section of the address window accessed by the request for entry i. Each of the subrequests is processed in the same manner as sequential descriptor entries before processing the next entry in the descriptor table 400.

From the no branch of block 456 or block 458, if (at block 460) the number of outstanding split requests does not exceed the maximum outstanding split transactions 254 indicated in the configuration registers 250, i.e., more split read requests may be issued, then the DMA 56 transmits (at block 462) the read request or one of the subrequests for entry 402 i to the memory address 406 i provided for entry 402 i. The outstanding split requests variable is incremented (at block 464) and control proceeds (at block 470) back to block 454 to process the next entry in the DMA descriptor table 400. If (at block 460) the maximum possible number of split requests are outstanding, then the DMA 56 waits (at block 466) for one split request to complete. After completing the split request, the DMA 56 decrements (at block 468) the outstanding split requests variable by one and proceeds to block 458 to transmit the next read request in the ith entry in the DMA descriptor table 400.

With the described embodiments, the address window for the disk controller 54 can be set to any size independent of the size of the I/O transaction received at the external bus master 52. Based on the configured address window, the I/O processor embodiment determine the maximum number of outstanding split-read requests that the external bus master DMA 56 may submit in order to process a received I/O transaction that is larger than the address window. By setting the maximum outstanding split transactions 254 to not cause the number of bytes of the outstanding split requests to exceed the number of bytes in the address window, which embodiment require reusing addresses in the address window, the I/O processor 70 ensures that the disk controller 54 can determine the order in which requests were initiated and return requested data to the correct request. In this way, the external bus master 52 is certain of the read request associated with data returned from the disk controller 54.

Returning Data to Read Requests

FIG. 11 illustrates an alternative embodiment of the system 50 shown in FIG. 2, where the components 552, 554, 556, 558, 560 a . . . 560 n, 564, 570, and 572 in the system 550 in FIG. 11 may comprise the same components 52, 54, 56, 58, 60 a . . . 60 n, 64, 70, and 72 shown in FIG. 2. In addition, the system 500 in FIG. 11 includes a bridge 574 between the external bus master 552 and the bus 572 connecting to the disk controller 554. Another bus 576 connects the external bus master 552 to the bridge 574. In PCI and PCI-X embodiments, a bridge, such as bridge 574, may forward read requests, such as split read requests, out of order with respect to the order in which they were made by the original initiator, e.g., external bus master 552. This may result in the bridge 574 forwarding a later sent read request before an earlier sent request.

In the above described embodiments, the disk controller 554 returns data from the buffer 564 that was read from the disk 560 a . . . 560 n in response to a request to an address in the address window. If the external bus master 552 requests sequential data from sequential addresses in the address window, then the external bus master 552 expects the data to be returned to the sequential requests in the order in which the requests were generated. However, if the disk controller 554 returns data from the buffer 564 to a request to an address that follows a request to a previous address that has not been processed, then the disk controller 554 may return the data out of order. For instance, PCI and PCI-X bridges may forward requests out of order. In such case, if the disk controller 554 responds to a read request received out of the sequential order in which the requests were issued, then the disk controller 554 may return data out of order such that data may be returned to a subsequent request when the data should have been returned to a previously issued request not yet received.

In certain described embodiments, the disk controller 554 returns data to requests from the external bus master 552 according to the order in which the requests were initiated by the external bus master DMA 556 regardless of whether the requests are received out of their sequential ordering. In this way, data is returned sequentially to the requests in the order in which the requests were issued, such that each transmitted request will access a sequential portion of the data requested from disk 560 a . . . 560 n. To return sequential data to the requests in the order in which the requests were initiated by the external bus master 552, the disk controller 554 maintains a request queue 578 to buffer read requests, such as split read requests, from the external bus master 552 received out of order. The disk controller 554 further maintains a next address variable 580 indicating the address of the next request that should be received that sequentially follows the previously processed request. In the described embodiments, the external bus master 552 issues requests sequentially to addresses in the address window, such that a subsequent request should be directed to the address that immediately follows the target address plus the byte count of the previous request. In certain embodiments, the request queue 578 may be of sufficient size to queue the maximum number of read requests that may be outstanding at once from the external bus master 554, which may comprise the maximum outstanding split transactions 254 (FIG. 6) setting for the external bus master 552.

The request queue 578 may include information provided with each read request transmitted from the external bus master 552. FIG. 12 illustrates information maintained with each request entry 590 in the request queue 578, where each entry 590 may include request information 592 to identify the request, the target address of the request 594 within the address window for the target device, e.g., disks 560 a . . . 560 n, and a byte count 596 of the request.

In certain embodiments, every read request may specify the same request byte size. In alternative embodiments, each read request may specify a different byte size when accessing contiguous addresses in the address window. In certain embodiments, the read requests may comprise read requests, such as split read requests, sent from the external bus master DMA 556 when processing a descriptor table generated by the I/O processor 570 according to the logic of FIG. 8.

FIG. 13 illustrates logic implemented in the disk controller 554 to return data to split read requests. Control begins with the disk controller receiving (at block 600) indication that split read requests will be received. This indication may comprise the I/o processor 570 sending the command to buffer and access data for an I/O request, such as the signal the I/O processor 570 sends at block 374 in FIG. 8. The disk controller 554 sets (at block 602) a next address variable 580 indicating the address for the expected next sequential split read request to the base, or first, address in the disk controller 554 address window. Upon receiving (at block 604) a split read request to an address in the address window from the external bus master 552, the disk controller 554 determines (at block 606) whether the received request is to an address that is the same address indicated in the next address variable 580. If not, then the disk controller 554 queues (at block 608) the received split read request in the request queue 578, where the queued request 590 may include the request information 592, the target address 594, and the byte count 596 of the request. If (at block 606) the target address of the received request is the same as the address indicated in the next address variable 580, then the disk controller 554 returns (at block 610) a data packet (if currently available in the buffer 564) to the received request having a number of bytes from the buffer 564 equal to the byte count indicated in the received split read request. In certain embodiments, the buffer 564 queues data accessed from the disks 560 a . . . 560 n on a FIFO basis, such that the data returned is accessed from the “first-in” end of the buffer 564.

After returning the data, if (at block 612) the next address variable 580 plus the byte count of the returned request is equal to the last address in the address window, i.e., there are no more sequential address remaining in the address window following the last request, then the next address variable 580 is set (at block 614) to the base address because the addresses roll over to the base address. Otherwise, if there are addresses in the address window following the last request, then the disk controller 554 increments (at block 616) the next address variable 580 by the byte count of the request to which data was just returned because the next request will be directed to the next sequential address following the last address of the previously processed request.

After incrementing the next address variable 580 to the address of the next sequential read request at block 614 or 616, the disk controller 554 determines (at block 618) whether one queued read request in the request queue 578 has a same target address 594 (FIG. 12) as the next address variable 580, i.e., the address of the next expected sequential split read request that was previously received and placed in the request queue 578. If not, control returns to block 604 to wait for the next split read request. Otherwise, the disk controller 554 dequeues (at block 620) the request having the same address. When dequeuing the request having the same address (at block 620), the disk controller 554 accesses (at block 622) a number of bytes from the buffer 564 equal to the byte count of the dequeued request and returns (at block 624) the accessed bytes to the dequeued request in a manner known in the art. From block 624 control proceeds to block 612 to set the next address variable 580 to the address of the next sequential read request to process.

FIG. 14 provides a table illustrating how four sequential read requests 1, 2, 3, and 4, each one kilobyte in length and issued by the external bus master 552, are processed in accordance with the logic of FIG. 13. In the example of FIG. 14, the disk controller 554 receives requests 1, 2, 3, and 4 to sequential addresses in the address window in the reverse order in which they were initiated by the external bus master 552. As shown, data is not returned to a request until data is returned to the request to previous sequential addresses. Until data is returned to the previous request, the request is queued.

With the described embodiments, if the disk controller 554 receives split read requests out of order due to request processing by a bridge 574 or for some other reason, then the disk controller 554 will queue requests received out of order and only return data to a request that is the next expected read request. In this way, the disk controller 554 sequentially returns data to the split read requests in the order in which the split read requests were initiated by the external bus master 552. This ensures that the external bus master 552 receives data returned to the appropriate read requests, such that data is returned to sequential requests in the sequential order in which they were intended to be serviced.

Additional Embodiments

The operations and logic described herein may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The term “article of manufacture” as used herein refers to machine readable instructions or logic implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.) or a machine readable medium (e.g., magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.). Code in the computer readable medium is accessible and executable by a processor. The code in which preferred embodiments are implemented may further be accessible through a transmission media or from a file server over a network. In such cases, the article of manufacture in which the code is implemented may comprise a transmission media, such as a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention, and that the article of manufacture may comprise any information bearing medium known in the art.

In the described implementations, the processing devices 52, 54, and 70 communicate on a bus topology, such as a PCI-X or PCI bus topology. In alternative implementations, the processing devices 52, 54, and 70 may communicate using any communication architecture known in the art.

In PCI bus implementations, additional PCI-X or PCI bridges may be located between any of the processing devices 52, 54, and 70 and the bus 72 to enable communication on the bus 72. For instance, in PCI-X implementations, the external bus master 52 may transmit burst read requests to a bridge, which may then forward the request to bus 72 to fetch the exact amount of requested data.

In certain implementations, the disk drives 60 a . . . 60 n comprised magnetic hard disk drives. In alternative implementations, the storage devices connected to the disk controller 54 may comprise any storage device known in the art, such as optical disks, tapes, etc.

In the described implementations, the initiator uses the address window to submit requests to a disk controller. In alternative implementations, the target disk controller may comprise any type of Input/Output controller device known in the art, in addition to storage related controllers. Further, the initiator or external bus master 52 may be any device that initiates requests to the disk controller, such as a host bus adaptor or other external device.

The logic of FIGS. 4 and 5 describes specific operations occurring in a particular order. In alternative implementations, certain of the logic operations may be performed in a different order, modified or removed. Morever, steps may be added to the above described logic and still conform to the described implementations. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units. In further embodiments, the address window might be set to a smaller size to allow for address windows for multiple target devices, such as disk controllers, so that each target device may have a unique range of the address window. This allows the external bus master to directly access any of multiple target devices by sending data requests to memory addresses in the address window configured for the specific target device.

In the described embodiments, the received read requests comprised split read requests. Alternatively, the requests processed according to the logic described above may comprise any type of bus request to which data is returned.

In the above described embodiments, the disk controller maintained the address of the next sequential request issued by the external bus master that should be received to determine whether requests were received out of order. In alternative embodiments, the disk controller may perform alternative operations to determine whether at least one read request for sequential data preceding the data requested by the received read request was not processed, i.e., whether the current received request is for data that follows data requested by previous requests which have not been processed. Alternative calculations, flags and/or other indicators may be used to determine whether transmitted requests are received out of order.

The foregoing description of the preferred embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. 

What is claimed is:
 1. A method, comprising: receiving a read request that is one of a plurality of read requests directed toward sequential data; determining whether previous read request for sequential data preceding the data requested by the received read request was returned; and returning data to the received read request in response to determining that requested data was returned to the previous read request.
 2. The method of claim 1, further comprising: queuing the received read request in response to an absence of returning data to the at least one previous read request.
 3. The method of claim 2, further comprising: in response to returning data to the received read request, determining whether one queued read request is for sequential data following the sequential data returned to the received read request; and returning data to the queued read request for sequential data following the sequential data returned to the received read request.
 4. The method of claim 3, wherein determining whether one queued read request is for sequential data comprises determining whether one queued read request is for sequential data immediately following the sequential data returned to the received read request.
 5. The method of claim 1, wherein the read requests are for sequential addresses in an address window used to access sequential data from a target device.
 6. The method of claim 5, further comprising: storing sequential data received from the target device in a First-In-First-Out (FIFO) buffer, wherein data from the buffer is returned to the received read requests on a FIFO basis.
 7. The method of claim 5, wherein determining whether the at least one previous read request for sequential data preceding the data requested by the received read request was processed comprises: determining an address in the address window immediately following a last address of a most recently processed previous read request to which data was returned; and determining whether the received read request requests data at the determined address, wherein the at least one previous read request was processed if the received read request starts at the determined address.
 8. The method of claim 7, wherein determining the address in the address window immediately following the last address of the last processed previous read request to which data was returned comprises: summing a byte count of the last processed previous read request and the starting address of the last processed previous read request.
 9. The method of claim 8, wherein determining the address in the address window immediately following the last address in the last processed previous read request to which data was returned further comprises: determining whether a result of the summing operation equals a last address in the address window, wherein the determined address is a first address in the address window if the result of the summing operation is equal to the last address in the address window and wherein the determined address is the result of the summing operation if the result of the summing operation is less than the last address in the address window.
 10. The method of claim 7, further comprising: queuing the received read request if data was not returned to the at least one previous read request; determining whether one queued read request targets data starting from the determined address; and returning data to the queued read request that targets data at the determined address.
 11. The method of claim 10, wherein the determination of whether one queued read request targets data starting from the determined address occurs after returning data to the received read request.
 12. The method of claim 11, wherein the determination of whether one queued read request targets data starting from the determined address occurs after determining that the received read request is not for data at the determined address.
 13. The method of claim 4, wherein the target device comprises a non-volatile storage medium.
 14. A system, comprising: a device including date; a controller capable of accessing data in the device, wherein the controller is capable of performing: (a) receiving a read request that is one of a plurality of read requests directed toward sequential data; (b) determining whether previous read request for sequential data preceding the data requested by the received read request was returned; and (c) returning data to the received read request in response to determining that requested data was returned to the previous read request.
 15. The system of claim 14, wherein the controller further performs: queuing the received read request in response to an absence of returning data to the at least one previous read request.
 16. The system of claim 15, wherein the controller further performs: in response to returning data to the received read request, determining whether one queued read request targets sequential data following the sequential data returned to the received read request; and returning data to the queued read request for sequential data following the sequential data returned to the received reed request.
 17. The system of claim 14, wherein the read requests are for sequential addresses in an address window used to access sequential data from the device.
 18. The system of claim 17, wherein the controller determines whether the at least one previous read request for sequential data preceding the data requested by the received read request was processed by: determining an address in the address window immediately following a last address of a most recently processed read request to which data was returned; and determining whether the received read request requests data at the determined address, wherein the at least one previous read request was processed if the received read request starts at the address that is the determined address.
 19. The system of claim 17, wherein the controller further performs: queuing the received read request if data was not returned to the at least one previous read request; determining whether one queued read request targets data starting from the determined address; and returning data to the queued read request that targets data at the determined address.
 20. A system, comprising: a bus; an initiator coupled to the bus; a device including data; and a controller coupled to the bus and capable of accessing data in the device, wherein the controller is adapted to perform: (i) receiving a read request that is one of a plurality of read requests directed toward sequential data; (ii) determining whether previous read request for sequential data preceding the data requested by the received read request was returned; and (iii) returning data to the received read request in response to determining that requested data was returned to the previous read request.
 21. The system of claim 20, wherein the controller is further adapted to perform: queuing the received read request in response to an absence of data returned to the at least one previous read request.
 22. The system of claim 21, wherein the controller is further adapted to perform: determining, in response to returning data to the received read request, whether one queued read request targets sequential data following the sequential data returned to the received read request; and returning data to the queued read request for sequential data following the sequential data returned to the received read request.
 23. The system of claim 20, wherein the read requests are for sequential addresses in an address window used to access sequential data from the device.
 24. The system of claim 23, wherein determining whether the at least one previous read request for sequential data preceding the data requested by the received read request was processed further comprises: determining an address in the address window immediately following a last address of a most recently processed previous read request to which data was returned; and determining whether the received read request requests data starting at the determined address, wherein the at least one previous read request was processed if the received read request starts at the address that is the determined address.
 25. The system of claim 24, wherein the controller is further adapted to perform: queuing the received read request if data was not returned to the at least one previous read request; determining whether one queued read request targets data starting from the determined address; and returning data to the queued read request that targets data at the determined address.
 26. An article of manufacture, wherein the article of manufacture is capable of causing operations to be performed, the operations comprising: receiving a read request that is one of a plurality of read requests directed toward sequential data; determining whether previous read request for sequential data preceding the data requested by the received read request was returned; and returning data to the received read request in response to determining that requested data was returned to the previous read request.
 27. The article of manufacture of claim 26, further comprising: queuing the received read request in response to an absence of a return of data to the at least one previous read request.
 28. The article of manufacture of claim 27, farther comprising: in response to returning data to the received read request, determining whether one queued read request targets sequential data following the sequential data returned to the received read request; and returning data to the queued read request for sequential data following the sequential data returned to the received read request.
 29. The article of manufacture of claim 28, wherein determining whether one queued read request targets sequential data comprises determining whether one queued read request targets sequential data immediately following the sequential data returned to the received read request.
 30. The article of manufacture of claim 26, wherein the read requests are for sequential addresses in an address window used to access sequential data from a target device.
 31. The article of manufacture of claim 30, further comprising: storing sequential data received from the target device in a First-In-First-Out (FIFO) buffer, wherein data from the buffer is returned to the received read requests on a FIFO basis.
 32. The article of manufacture of claim 30, wherein determining whether the at least one previous read request for sequential data preceding the data requested by the received read request were processed comprises: determining an address in the address window immediately following a last address of a most recently processed read request to which data was returned; and determining whether the received read request requests data at the determined address, wherein the at least one previous read request was processed if the received read request starts at the address that is the determined address.
 33. The article of manufacture of claim 32, wherein determining the address in the address window immediately following the last address of the last processed previous read request to which data was returned comprises: summing a byte count of the last processed previous read request and the starting address of the last processed previous read request.
 34. The article of manufacture of claim 33, wherein determining the address in the address window immediately following the last address in the last processed previous read request to which data was returned further comprises: determining whether a result of the summing operation is equal to a last address in the address window, wherein the determined address is a first address in the address window if the result of the summing operation is equal to the last address in the address window and wherein the determined address is the result of the summing operation if the result of the summing operation is less than the last address in the address window.
 35. The article of manufacture of claim 33, further comprising: queuing the received read request if data was not returned to the at least one previous read request; determining whether one queued read request targets data starting from the determined address; and returning data to the queued read request that targets data at the determined address.
 36. The article of manufacture of claim 35, wherein the determination of whether one queued read request targets data starting from the determined address occurs after returning data to the received read request.
 37. The article of manufacture of claim 35, wherein the determination of whether one queued read request targets data starting from the determined address occurs after determining that the received read request is not for data at the determined address.
 38. The article of manufacture of claim 29, wherein the target device comprises a non-volatile storage medium. 